Skip to content

42. How to begin the journy of open source (first contribution) #2182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 9, 2024

Conversation

MrCodYrohit
Copy link
Contributor

I added in README.md as 42. How to begin the journy of open source (first contribution), this YT video contains the following steps:

Beginning your journey into open source can be both exciting and daunting. Here's a step-by-step guide to help you make your first contribution:

  1. Choose a Project:

    • Start by identifying an open-source project that interests you. It could be a software library, an application, a framework, or even documentation.
    • Consider projects that align with your interests, skills, and level of expertise.
  2. Research the Project:

  • Familiarize yourself with the project's goals, codebase, and contribution guidelines.
  • Read the project's documentation, including the README file, contributing guidelines, and code of conduct.
  1. Find an Issue:
  • Look for beginner-friendly or "good first issue" labels in the project's issue tracker.
  • Issues marked as such are usually well-suited for newcomers and often have detailed instructions on how to solve them.
  1. Setup Your Development Environment:

    • Follow the project's instructions to set up your local development environment.
    • This may involve installing specific software, configuring dependencies, and cloning the project's repository.
  2. Solve the Issue:

    • Once you've chosen an issue to work on, fork the project's repository to your GitHub account.
    • Create a new branch for your changes. Make sure to give it a descriptive name related to the issue you're addressing.
    • Write clean, well-commented code following the project's coding conventions and style guidelines.
    • Test your changes thoroughly to ensure they work as expected.
  3. Submit a Pull Request (PR):

    • Once your changes are ready, commit them to your branch and push them to your forked repository.
    • Open a pull request from your branch to the original project's repository.
    • Provide a clear and concise description of the changes you've made in the PR description.
    • If the project has a contributing template, make sure to fill it out completely.
  4. Collaborate and Iterate:

    • Be prepared to receive feedback on your pull request from maintainers and other contributors.
    • Address any comments or suggestions promptly, making necessary changes to your code.
    • Collaboration and iteration are key aspects of the open-source culture, so embrace feedback as an opportunity to learn and improve.
  5. Celebrate Your Contribution:

    • Once your pull request is accepted and merged into the main project, celebrate your contribution to the open-source community!
    • Your code is now part of a larger ecosystem and can potentially benefit countless users worldwide.

Additional Tips:

  • Don't be afraid to ask questions if you're unsure about anything.
  • Be patient and persistent. Contributing to open source can sometimes be challenging, but it's also incredibly rewarding.
  • Consider contributing to documentation, testing, or bug triaging if you're not ready to dive into code just yet.

Remember, the journey of open source is all about learning, collaborating, and making a positive impact on the community. So, don't hesitate to take that first step!

@geekcomputers geekcomputers merged commit 624e8a9 into geekcomputers:master May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants